Skip to content

feat : update studio docs#675

Open
Ayush0054 wants to merge 1 commit into
mainfrom
studio-docs-update
Open

feat : update studio docs#675
Ayush0054 wants to merge 1 commit into
mainfrom
studio-docs-update

Conversation

@Ayush0054
Copy link
Copy Markdown
Member

Description

Describe key changes, mention related issues or motivation for the changes.

Note: Your PR title must follow conventional commit format (e.g., docs: add auth guide, fix: correct broken links, style: update formatting). See CONTRIBUTING.md for details.

Type of Change

  • Bug fix (errors, broken links, outdated info)
  • New content
  • Content improvement
  • Other: ____

Related Issues/PRs (if applicable)

  • Closes #____
  • Related SDK PR: agno-agi/agno#____

Checklist

  • Content is accurate and up-to-date
  • All links tested and working
  • Code examples verified (if applicable)
  • Spelling and grammar checked
  • Screenshots updated (if applicable)

@mintlify
Copy link
Copy Markdown

mintlify Bot commented Jun 3, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
agno 🟢 Ready View Preview Jun 3, 2026, 4:53 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Copy link
Copy Markdown
Contributor

@mishramonalisha76 mishramonalisha76 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add a small video of creating agent, team and workflows , individual pages or maybe one in the overview ?

Can we make all the image to be of the whole app witht he sidebar and topbar?

| **Input/Output Schema** | Structured I/O using registered Pydantic schemas |
| **Memory** | Enable memory for multi-turn conversations |
| **Knowledge** | Attach knowledge bases for RAG |
- **Model**: select from registered models.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we also give the sdk version from when studio is available ?

| [Teams](/agent-os/studio/teams) | Compose multi-agent teams with coordination modes |
| [Workflows](/agent-os/studio/workflows) | Design step-based workflows with conditions, loops, routers, and parallel execution |
| [Registry](/agent-os/studio/registry) | Browse and manage registered tools, models, databases, and schemas |
**[Agents](/agent-os/studio/agents)**
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**[Agents](/agent-os/studio/agents)**
**[Agents](/agent-os/studio/agents)** :

**[Workflows](/agent-os/studio/workflows)**
Orchestrate agents and teams into step-based pipelines. Control the flow with loops, conditions, routers, and parallel execution.

use functions or cel expressions to evaluate conditions and selectors.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this belong to workflows only or agent and teams too ? looks like an orphaned line

Comment on lines +22 to +26
Add tools, models, databases, and schemas that Studio can use to build agents, teams, and workflows.

Register agents and teams in the `Registry` to reuse them as members in Studio teams and as steps in Studio workflows.

Register `knowledge`, `memory_managers`, and `session_summary_managers` for agents and teams to use.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Add tools, models, databases, and schemas that Studio can use to build agents, teams, and workflows.
Register agents and teams in the `Registry` to reuse them as members in Studio teams and as steps in Studio workflows.
Register `knowledge`, `memory_managers`, and `session_summary_managers` for agents and teams to use.
Register the components Studio composes with: tools, models, databases, schemas, knowledge, `memory_managers`, and `session_summary_managers`. Register existing agents and teams to reuse them as members in Studio teams or steps in Studio workflows.


Save your work as a draft version. Drafts are not accessible via the API but can be tested, restored, and published later. You can save multiple draft versions to checkpoint your progress.

### 2. Save Draft or publish directly
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### 2. Save Draft or publish directly
### 2. Save Draft or Publish Directly

Comment thread agent-os/studio/teams.mdx
| **Success Criteria** | Define when the team's task is complete |
Create a new team by using existing agents and teams from your Registry or built in Studio, and configuring the team settings:

- **Team Members and Execution**: select agents or teams to include as members, and set the team mode and delegation behavior. read more about [team members and execution](/agent-os/studio/teams#team-members-and-execution) here.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **Team Members and Execution**: select agents or teams to include as members, and set the team mode and delegation behavior. read more about [team members and execution](/agent-os/studio/teams#team-members-and-execution) here.
- **Team Members and Execution**: select agents or teams to include as members, and set the team mode and delegation behavior. Read more about [team members and execution](/agent-os/studio/teams#team-members-and-execution) here.

Comment thread agent-os/studio/teams.mdx
### Team Members and Execution

- **Members**: select the agents or teams to include as members.
- **Team Mode** _(optional)_: controls how the team leader coordinates work with member agents:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should attach some reference doc for this if available

Comment thread agent-os/studio/teams.mdx
- **Route**
- **Broadcast**
- **Tasks**
- **Respond Directly**: let the team leader respond on its own instead of delegating.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **Respond Directly**: let the team leader respond on its own instead of delegating.
- **Respond Directly**: lets the team leader respond on its own instead of delegating.

Comment thread agent-os/studio/teams.mdx
- **Broadcast**
- **Tasks**
- **Respond Directly**: let the team leader respond on its own instead of delegating.
- **Delegate to All Members**: send the task to every member at once.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **Delegate to All Members**: send the task to every member at once.
- **Delegate to All Members**: sends the task to every member at once.




example of registry configuration:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
example of registry configuration:
Example of registry configuration:

Copy link
Copy Markdown
Contributor

@mishramonalisha76 mishramonalisha76 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets also connect each page to the respective API reference

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants